From eceb165013a2bba8f4aaca34aa8dc01f4633d152 Mon Sep 17 00:00:00 2001 From: Colin Walters Date: Fri, 23 Dec 2016 09:59:30 -0500 Subject: [PATCH] docs: Fix ostree.version -> version I think originally I had envisioned this as `ostree.version`, but at the last minute we changed it to just `version`. That's what all of the code uses, so let's fix the docs. Closes: #638 Approved by: paulvt --- docs/manual/repository-management.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/manual/repository-management.md b/docs/manual/repository-management.md index 5688a582..64b2f6e1 100644 --- a/docs/manual/repository-management.md +++ b/docs/manual/repository-management.md @@ -154,7 +154,7 @@ and generate a new commit in our prod repository: checksum=$(ostree --repo=repo-dev rev-parse exampleos/x86_64/stage-3-pass/standard`) ostree --repo=repo-prod pull-local repo-dev ${checksum} ostree --repo=repo-prod commit -b exampleos/x86_64/standard \ - -s 'Release 1.2.3' --add-metadata-string=ostree.version=1.2.3 \ + -s 'Release 1.2.3' --add-metadata-string=version=1.2.3 \ --tree=ref=${checksum} ``` @@ -171,7 +171,7 @@ links to avoid copying any content at all - making the process very fast. Another interesting thing to notice here is that we're adding an -`ostree.version` metadata string to the commit. This is an optional +`version` metadata string to the commit. This is an optional piece of metadata, but we are encouraging its use in the OSTree ecosystem of tools. Commands like `ostree admin status` show it by default. -- 2.30.2